Linking instances within a cloud computing environment

ABSTRACT

Embodiments of the present invention provide an approach to allow a user to link multiple cloud instances (e.g., virtual machines) together such that an action on one (cloud) instance is triggered when a second instance&#39;s state changes thereby invoking a predefined set of rules. Specifically, instances can be linked to one another via a graphical user interface (GUI or the like), and associated with a set of rules. The set of rules indicates a behavior/reaction of one instance when an action is performed with respect to another instance linked thereto. These embodiments could be implemented external to or within a cloud operating environment.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent document is a continuation of U.S. patent applicationSer. No. 14/628,490, filed Feb. 23, 2015, which is a continuation ofU.S. patent application Ser. No. 12/887,773, filed Sep. 22, 2010, nowU.S. Pat. No. 9,043,445, issued May 26, 2015. The entire contents ofeach of such applications are incorporated herein by reference.

TECHNICAL FIELD

The present invention generally relates to instance linking.Specifically, the present invention relates to the linking of instances(e.g., virtual machines) within a cloud computing environment.

BACKGROUND

The cloud computing environment is an enhancement to the predecessorgrid environment, whereby multiple grids and other computation resourcesmay be further abstracted by a cloud layer, thus making disparatedevices appear to an end-user as a single pool of seamless resources.These resources may include such things as physical or logical computeengines, servers and devices, device memory, storage devices.

Currently, it is difficult in cloud computing environments for users tolink (or create relationships) among multiple instances so that thechange in status of one instance will be reflected in the status ofanother instance. Linking instance can be especially important wheninstances rely upon each other. Today, semantic relationships are notcaptured as part of instance provisioning. Rather, it is the user thatoften understands the relationships and roles between virtual machines.As such, the user will typically make the changes manually, or monitorand implement some level of automation external to the operatingenvironment.

SUMMARY

Embodiments of the present invention provide an approach to allow a userto link multiple cloud instances (e.g., virtual machines) together suchthat an action on one (cloud) instance is triggered when a secondinstance's state changes thereby invoking a predefined set of rules.Specifically, instances can be linked to one another via a graphicaluser interface (GUI or the like), and associated with a set of rules.The set of rules indicates a behavior/reaction of one instance when anaction is performed with respect to another instance linked thereto.These embodiments could be implemented external to or within a cloudoperating environment.

A first aspect of the present invention provides a method for linkinginstances within a cloud computing environment, comprising: starting afirst cloud instance; associating the first cloud instance with a set ofrules, the set of rules indicating a reaction of a second cloud instancelinked to the first instance when an action is performed with respect tothe first cloud instance; performing an action on the first cloudinstance; and causing the reaction of the second cloud instance,according to the set of rules, in response to the action.

A second aspect of the present invention provides a system for linkinginstances within a cloud computing environment, comprising: a bus; aprocessor coupled to the bus; and a memory medium coupled to the bus,the memory medium comprising instructions to: start a first cloudinstance; associate the first cloud instance with a set of rules, theset of rules indicating a reaction of a second cloud instance linked tothe first instance when an action is performed with respect to the firstcloud instance; perform an action on the first cloud instance; and causethe reaction of the second cloud instance, according to the set ofrules, in response to the action.

A third aspect of the present invention provides a computer programproduct for linking instances within a cloud computing environment, thecomputer program product comprising a computer readable storage media,and program instructions stored on the computer readable storage media,to: start a first cloud instance; associate the first cloud instancewith a set of rules, the set of rules indicating a reaction of a secondcloud instance linked to the first instance when an action is performedwith respect to the first cloud instance; perform an action on the firstcloud instance; and cause the reaction of the second cloud instance,according to the set of rules, in response to the action.

A fourth aspect of the present invention provides a method for deployinga system for linking instances within a cloud computing environment,comprising: deploying a computer infrastructure being operable to: starta first cloud instance; associate the first cloud instance with a set ofrules, the set of rules indicating a reaction of a second cloud instancelinked to the first instance when an action is performed with respect tothe first cloud instance; perform an action on the first cloud instance;and cause the reaction of the second cloud instance, according to theset of rules, in response to the action.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readilyunderstood from the following detailed description of the variousaspects of the invention taken in conjunction with the accompanyingdrawings in which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 depicts a cloud manager according to an embodiment of the presentinvention

FIG. 5 depicts a first graphical user interface (GUI) showing linkedinstances according to an embodiment of the present invention.

FIG. 6 depicts a second GUI that was provisioned in response to aprovisioning of a first instance according to an embodiment of thepresent invention.

FIG. 7 depicts a method according to an embodiment of the presentinvention.

The drawings are not necessarily to scale. The drawings are merelyschematic representations, not intended to portray specific parametersof the invention. The drawings are intended to depict only typicalembodiments of the invention, and therefore should not be considered aslimiting the scope of the invention. In the drawings, like numberingrepresents like elements.

DETAILED DESCRIPTION

Exemplary embodiments now will be described more fully herein withreference to the accompanying drawings, in which exemplary embodimentsare shown. This disclosure may, however, be embodied in many differentforms and should not be construed as limited to the exemplaryembodiments set forth herein. Rather, these exemplary embodiments areprovided so that this disclosure will be thorough and complete and willfully convey the scope of this disclosure to those skilled in the art.In the description, details of well-known features and techniques may beomitted to avoid unnecessarily obscuring the presented embodiments.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of this disclosure.As used herein, the singular forms “a”, “an”, and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Furthermore, the use of the terms “a”, “an”, etc., do notdenote a limitation of quantity, but rather denote the presence of atleast one of the referenced items. It will be further understood thatthe terms “comprises” and/or “comprising”, or “includes” and/or“including”, when used in this specification, specify the presence ofstated features, regions, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, regions, integers, steps, operations, elements,components, and/or groups thereof.

Embodiments of the present invention provide an approach to allow a userto link multiple cloud instances (e.g., virtual machines) together suchthat an action on one (cloud) instance is triggered when a secondinstance's state changes thereby invoking a predefined set of rules.Specifically, instances can be linked to one another via a graphicaluser interface (GUI or the like), and associated with a set of rules.The set of rules indicates a behavior/reaction of one instance when anaction is performed with respect to another instance linked thereto.These embodiments could be implemented external to or within a cloudoperating environment.

It is understood in advance that although this disclosure includes adetailed description of cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded, automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication-hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10, there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing unit 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM, or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

The embodiments of the invention may be implemented as a computerreadable signal medium, which may include a propagated data signal withcomputer readable program code embodied therein (e.g., in baseband or aspart of a carrier wave). Such a propagated signal may take any of avariety of forms including, but not limited to, electro-magnetic,optical, or any suitable combination thereof. A computer readable signalmedium may be any computer readable medium that is not a computerreadable storage medium and that can communicate, propagate, ortransport a program for use by or in connection with an instructionexecution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium including, but not limited to, wireless,wireline, optical fiber cable, radio-frequency (RF), etc., or anysuitable combination of the foregoing.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as private, community,public, or hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms, and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes. In oneexample, IBM® zSeries® systems and RISC (Reduced Instruction SetComputer) architecture based servers. In one example, IBM pSeries®systems, IBM xSeries® systems, IBM BladeCenter® systems, storagedevices, networks, and networking components. Examples of softwarecomponents include network application server software. In one example,IBM WebSphere® application server software and database software. In oneexample, IBM DB2® database software. (IBM, zSeries, pSeries, xSeries,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide.)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provides pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and instance linking. As mentioned above, all of theforegoing examples described with respect to FIG. 3 are illustrativeonly, and the invention is not limited to these examples.

It is understood all functions of the present invention as describedherein are typically performed by the instance linking, which can betangibly embodied as modules of program code 42 of program/utility 40(FIG. 1). However, this need not be the case. Rather, the functionalityrecited herein could be carried out/implemented and/or enabled by any ofthe layers 60-66 shown in FIG. 3.

It is reiterated that although this disclosure includes a detaileddescription of cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather, theembodiments of the present invention are intended to be implemented withany type of clustered computing environment now known or laterdeveloped.

As indicated above, embodiments of the present invention allow for(among other things) instances to be linked so that when an action isperformed with respect to an instance, a corresponding reaction iscaused to one or more other instances linked thereto. Typically, suchbehavior is specified by a set of (predetermined) rules. For example,the set of rules could resemble the following:

1. Restart instance A when instance B is restarted.

2. Delete instance A when instance B is deleted.

3. Start instance A when instance B is started.

4. Start instance A when instance B is stopped.

5. Create new copy of instance B when instance B fails.

6. Create instance A when instance B is active.

Referring now to FIG. 4, these concepts will be explained in greaterdetail. As depicted, a cloud manager 70 or the like will receive arequest to link instances 72A. It is understood that cloud manager 70could be implemented as a computer program 40 (FIG. 1) having on or moremodules 42 (FIG. 1). In this example, a user has requested thatinstances A and B be linked to one another. Such a request could be madeusing any approach such as via a graphical user interface (e.g., via abutton, a link, a menu option, etc.). The result will be linkedinstances 74. In addition, cloud manger 70 can access a set of rules 76that specify how the instances will behave when a change is made to one(e.g., as shown above). Typically, rules 76 are configurable by a user,and can be set forth in any frequency (e.g., perform weekly) or quantity(e.g., perform once) of actions/reactions. As further shown in FIG. 5,assume that an action request for instance A has been received by cloudmanager 70. In this case, cloud manager 70 will consult rules 76 todetermine whether the action on instance A (e.g., made pursuant torequest 72B) should be accompanied by a corresponding reaction oninstance B. Cloud manager 70 can then perform (or have performed) anyapplicable actions/reactions. Furthermore, cloud manager 70 isconfigured to communicate an alert 78 at any point among processes(e.g., when requests are received, when instances are linked, when rulesare changed, when actions/reactions are performed, etc.). Such alert 78can be made via any means (e.g., via text, email, phone, etc.)

Referring now to FIGS. 5-6, a graphical user interface (GUI 80)illustrating these concepts is shown in greater detail. As shown GUI 80comprises instance action buttons 82 for performing actions on aninstance (e.g., reboot, delete, create, etc.), tag field 84 for tagginginstances with keywords or the like, access control buttons 86 forgenerating security keys or the like, location information 88 (such asoperating system, internet protocol (IP) and hostname), and instancefields 90 where instances 92A-B are identified. In this example, the setof rules specify that when an instance 92A is provisioned, a second(mirror) instance 92B is automatically provisioned and linked thereto. Asecond GUI 94 corresponding to this second instance 90B is shown in FIG.6. This provides confirmation for the user that instance 90B was in factprovisioned in response to the provisioning of instance 90A.

Referring now to FIG. 7, a method flow diagram according to the presentinvention is shown. In step S1, a first cloud instance (e.g., a virtualmachine) is started. In step S2, the first cloud instance is associatedwith a set of rules. As indicated above, the set of rules typicallyindicates a reaction to be caused with respect to a second cloudinstance (e.g., a virtual machine) linked to the first instance when anaction is performed with respect to the first cloud instance (e.g.,pursuant to a request). Moreover, the set of rules can be generatedaccording to the preferences of a user. Still yet, the two instances canbe linked to one another pursuant to an indication made via a graphicaluser interface (GUI) with the linking being viewable on the GUI. In stepS3, an action is performed on the first cloud instance. In step S4, thereaction of the second cloud instance is caused, according to the set ofrules, in response to the action. At any point in time, an alert canalso be generated and sent to keep the user informed.

While shown and described herein as an instance linking solution, it isunderstood that the invention further provides various alternativeembodiments. For example, in one embodiment, the invention provides acomputer-readable/useable medium that includes computer program code toenable a computer infrastructure to provide instance linkingfunctionality as discussed herein. To this extent, thecomputer-readable/useable medium includes program code that implementseach of the various processes of the invention. It is understood thatthe terms computer-readable medium or computer-useable medium compriseone or more of any type of physical embodiment of the program code. Inparticular, the computer-readable/useable medium can comprise programcode embodied on one or more portable storage articles of manufacture(e.g., a compact disc, a magnetic disk, a tape, etc.), on one or moredata storage portions of a computing device, such as memory 28 (FIG. 1)and/or storage system 34 (FIG. 1) (e.g., a fixed disk, a read-onlymemory, a random access memory, a cache memory, etc.).

In another embodiment, the invention provides a method that performs theprocess of the invention on a subscription, advertising, and/or feebasis. That is, a service provider, such as a Solution Integrator, couldoffer to provide instance linking functionality. In this case, theservice provider can create, maintain, support, etc., a computerinfrastructure, such as computer system 12 (FIG. 1) that performs theprocesses of the invention for one or more consumers. In return, theservice provider can receive payment from the consumer(s) under asubscription and/or fee agreement and/or the service provider canreceive payment from the sale of advertising content to one or morethird parties.

In still another embodiment, the invention provides acomputer-implemented method for instance linking. In this case, acomputer infrastructure, such as computer system 12 (FIG. 1), can beprovided and one or more systems for performing the processes of theinvention can be obtained (e.g., created, purchased, used, modified,etc.) and deployed to the computer infrastructure. To this extent, thedeployment of a system can comprise one or more of: (1) installingprogram code on a computing device, such as computer system 12 (FIG. 1),from a computer-readable medium; (2) adding one or more computingdevices to the computer infrastructure; and (3) incorporating and/ormodifying one or more existing systems of the computer infrastructure toenable the computer infrastructure to perform the processes of theinvention.

As used herein, it is understood that the terms “program code” and“computer program code” are synonymous and mean any expression, in anylanguage, code, or notation, of a set of instructions intended to causea computing device having an information processing capability toperform a particular function either directly or after either or both ofthe following: (a) conversion to another language, code, or notation;and/or (b) reproduction in a different material form. To this extent,program code can be embodied as one or more of: an application/softwareprogram, component software/a library of functions, an operating system,a basic device system/driver for a particular computing device, and thelike.

A data processing system suitable for storing and/or executing programcode can be provided hereunder and can include at least one processorcommunicatively coupled, directly or indirectly, to memory elementsthrough a system bus. The memory elements can include, but are notlimited to, local memory employed during actual execution of the programcode, bulk storage, and cache memories that provide temporary storage ofat least some program code in order to reduce the number of times codemust be retrieved from bulk storage during execution. Input/outputand/or other external devices (including, but not limited to, keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening device controllers.

Network adapters also may be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems,remote printers, storage devices, and/or the like, through anycombination of intervening private or public networks. Illustrativenetwork adapters include, but are not limited to, modems, cable modems,and Ethernet cards.

The foregoing description of various aspects of the invention has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formdisclosed and, obviously, many modifications and variations arepossible. Such modifications and variations that may be apparent to aperson skilled in the art are intended to be included within the scopeof the invention as defined by the accompanying claims.

What is claimed is:
 1. A method for linking instances within a cloudcomputing environment, comprising: receiving information for generatinga set of rules, the information comprising: one or more actions that maybe performed with respect to the first cloud instance, and for eachaction of the one or more actions, a corresponding reaction to beperformed with respect to a second cloud instance; starting a firstcloud instance; generating, based on the information, the set of rules,the set of rules defining the corresponding reaction to be performedwith respect to the second cloud instance when the each action of theone or more actions is performed with respect to the first cloudinstance; performing an action on the first cloud instance; and causingthe reaction of the second cloud instance, according to the set ofrules, in response to the action.
 2. The method of claim 1, the actionbeing performed in response to a request.
 3. The method of claim 1, theset of rules being generated according to preferences of a user.
 4. Themethod of claim 1, further comprising linking the first cloud instancewith the second cloud instance.
 5. The method of claim 4, the linkingoccurring pursuant to an indication made via a graphical user interface(GUI), the linking being viewable on the GUI.
 6. The method of claim 1,further comprising generating an alert pursuant to the action and thereaction.
 7. The method of claim 1, the first cloud instance and thesecond cloud instance comprising virtual machines
 8. The method of claim1, wherein a solution service provider provides a computerinfrastructure that performs the method for one or more consumers.
 9. Asystem for linking instances within a cloud computing environment,comprising: a bus; a processor coupled to the bus; and a memory mediumcoupled to the bus, the memory medium comprising instructions to:receiving information for generating a set of rules, the informationcomprising: one or more actions that may be performed with respect tothe first cloud instance, and for each action of the one or moreactions, a corresponding reaction to be performed with respect to asecond cloud instance; starting a first cloud instance; generating,based on the information, the set of rules, the set of rules definingthe corresponding reaction to be performed with respect to the secondcloud instance when the each action of the one or more actions isperformed with respect to the first cloud instance; performing an actionon the first cloud instance; and causing the reaction of the secondcloud instance, according to the set of rules, in response to theaction.
 10. The system of claim 9, the action being performed inresponse to a request.
 11. The system of claim 9, the set of rules beinggenerated according to preferences of a user.
 12. The system of claim 9,the memory medium further comprising instructions to link, pursuant toan indication made via a graphical user interface (GUI), the first cloudinstance with the second cloud instance, the linking being viewable onthe GUI.
 13. The system of claim 9, the memory medium further comprisinginstructions to generate an alert pursuant to the action and thereaction.
 14. The system of claim 9, the first cloud instance and thesecond cloud instance comprising virtual machines.
 15. A computerprogram product for linking instances within a cloud computingenvironment, the computer program product comprising a computer readablestorage media, and program instructions stored on the computer readablestorage media, to: receive information for generating a set of rules,the information comprising: one or more actions that may be performedwith respect to the first cloud instance, and for each action of the oneor more actions, a corresponding reaction to be performed with respectto a second cloud instance; starting a first cloud instance; generate,based on the information, the set of rules, the set of rules definingthe corresponding reaction to be performed with respect to the secondcloud instance when the each action of the one or more actions isperformed with respect to the first cloud instance; perform an action onthe first cloud instance; and cause the reaction of the second cloudinstance, according to the set of rules, in response to the action. 16.The computer program product of claim 15, the action being performed inresponse to a request.
 17. The computer program product of claim 15, theset of rules being generated according to preferences of a user.
 18. Thecomputer program product of claim 15, further comprising programinstructions stored on the computer readable storage media to link,pursuant to an indication made via a graphical user interface (GUI), thefirst cloud instance with the second cloud instance, the linking beingviewable on the GUI.
 19. The computer program product of claim 15,further comprising program instructions stored on the computer readablestorage media to generate an alert pursuant to the action and thereaction.
 20. The computer program product of claim 15, the first cloudinstance and the second cloud instance comprising virtual machines.